End User Remote Enterprise Application Software Testing

ABSTRACT

A system and method for remote testing of enterprise software applications (ESA) allows one or more testers to remotely access an ESA and remotely test the ESA. In at least one embodiment, the ESA resides in a testing platform that includes one more computers that are provisioned for testing. “Provisioning” a computer system (such as one or more servers) refers to preparing, configuring, and equipping the computer system to provide services to one or more users. In at least one embodiment, the computer system is provisioned to create an ESA operational environment in accordance with a virtual desktop infrastructure (VDI) template interacting with virtualization software.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit under 35 U.S.C. § 119(e) and 37C.F.R. § 1.78 of U.S. Provisional Application No. 61/492,564, filed Jun.2, 2011, and entitled “End User Remote Enterprise Application SoftwareTesting”, which is incorporated by reference in its entirety.

BACKGROUND OF THE INVENTION Field of the Invention

The present invention relates in general to the field of informationprocessing, and more specifically to a system and method for allowingusers to remotely test enterprise application software.

Description of the Related Art

Enterprise application software (EAS), also known as enterprisesoftware, is software used in organizations, such as in a business orgovernment. Services provided by EAS are typically business-orientedtools such as online shopping and online payment processing, interactiveproduct catalogue, automated billing systems, security, contentmanagement, information technology service management, customerrelationship management, resource planning, business intelligence, humanresources management, manufacturing, application integration, and formsautomation. EAS is typically hosted on servers and provides simultaneousservices to a large number of users, typically over a computer network.EAS contrasts with a single-user application that is executed on auser's personal computer and serves only one user at a time.

Extensive testing of EAS generally precedes organization-widedeployment. Purchase of EAS often ranges from thousands of US dollars tomillions of US dollars. Also, computing platforms often vary fromorganization to organization. (A “computing platform” refers to aparticular hardware architecture and software framework that allows theEAS to execute.) Furthermore, EAS may have varying customizations fromorganization to organization. For these exemplary reasons and becausedeployment of EAS often affects many users within an organization,extensive testing of EAS should generally precede organization-widedeployment.

The testing process of EAS prior to organizational-wide deployment,involves several operations. FIG. 1 depicts one exemplary,pre-deployment EAS testing process 100. In operation 102, testingpersonnel request allocation of a new testing server or servers thatwill be used for EAS testing. Because EAS generally utilizes a number ofdifferent purposed servers, generally, multiple test servers areallocated for the purposes of EAS testing. The servers may be purposedas application servers, database servers, etc. Allocation of a newtesting server or servers takes time T₁, and T₁ can often take up to one(1) week and can involve acquiring a new testing server or servers,providing a working network environment, configuring the servers fortheir purpose, and segregating the test servers into a test environmentrather than a ‘live’ operational environment.

In operation 102, software is downloaded to the testing servers,installed, and the testing servers are setup. The software includes notonly the EAS but also, for example, software library files, Java™,database applications, etc. Operation 102 takes time T₂, and time T₂ canoften take up to one (1) additional week.

In operation 104, testing and problem reporting begins. A large part ofthe testing operation 104 involves problem reporting. Problem reportingoften involves setup issues, and 60-80% of all problems can often berelated to setup issues. Operation 104 takes time T₃, and time T₃ cantake 2-5 weeks or more. Problem reporting, trouble-shooting, andapplying fixes also requires a large amount of interfacing with the EASsupplier thereby incurring personnel costs by the EAS supplier.

Additionally, operations 102, 104, and 106 involve the allocation ofknowledgeable testing personnel. Delays, sometimes on the order ofmonths, may occur in obtaining personnel with the right mix of skills toconduct all of operations 102, 104, and 106.

Consequently, EAS deployment is often a 6-12 month process. Because ofthe large time delays involved in deploying EAS, the acquisition rate ofnew EAS software is relatively low compared with many other productpurchases.

SUMMARY OF THE INVENTION

In one embodiment of the present invention, a method includes receivinga request with a computer from an end user using a computer to access anenterprise software application (ESA) hosted by an EAS testing platformthat is remote from the computer used by the end user. The method alsoincludes receiving data from the computer to test the ESA, wherein theremote EAS testing platform is provisioned to emulate an actualoperating environment for which the ESA is being tested. The methodfurther includes testing the ESA in the computer.

In another embodiment of the present invention, an apparatus includes anenterprise software application (ESA) testing computer platform hostingan enterprise software application. The EAS testing platform includesone or more computers that are remote from a computer used by an enduser providing data to test an ESA. During operation, the EAS testingplatform is capable of receiving the data to test the ESA and to executethe ESA.

In a further embodiment of the present invention, a computer readablemedium includes code stored therein for comprising code stored thereinand executable by a processor for receiving a request with a computerfrom an end user using a computer to access an enterprise softwareapplication (ESA) hosted by an EAS testing platform that is remote fromthe computer used by the end user. The code is further executable by theprocessor for receiving data from the computer to test the ESA, whereinthe remote EAS testing platform is provisioned to emulate an actualoperating environment for which the ESA is being tested. The code isfurther executable by the processor for testing the ESA in the computer.

In another embodiment of the present invention, an apparatus includesmeans for receiving a request with a computer from an end user using acomputer to access an enterprise software application (ESA) hosted by anEAS testing platform that is remote from the computer used by the enduser. The apparatus further includes means for receiving data from thecomputer to test the ESA, wherein the remote EAS testing platform isprovisioned to emulate an actual operating environment for which the ESAis being tested. The apparatus also includes means for testing the ESAin the computer.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention may be better understood, and its numerousobjects, features and advantages made apparent to those skilled in theart by referencing the accompanying drawings. The use of the samereference number throughout the several figures designates a like orsimilar element.

FIG. 1 (labeled prior art) depicts a pre-deployment EAS testing process.

FIG. 2 depicts a remote EAS testing process.

FIG. 3 depicts an exemplary provisioning and ESA testing process.

FIG. 4 depicts a login web page.

FIG. 5 depicts an exemplary computer.

DETAILED DESCRIPTION

A system and method for remote testing of enterprise softwareapplications (ESA) allows one or more testers to remotely access an ESAand remotely test the ESA. Each tester is an actual person, and is anend user in that the tester actually tests the ESA via a testercomputer. In at least one embodiment, the ESA resides in an ESA testingplatform. An “EAS testing platform” includes a particular hardware andsoftware configuration that allows the EAS to execute and includes onemore computers that are provisioned for testing. “Remote” indicatesaccessibility via an extranet network, such as the Internet.“Provisioning” a computer system (such as one or more servers) refers topreparing, configuring, and equipping the computer system to provideservices to one or more users.

In at least one embodiment, the computer system is provisioned to createan ESA operational environment in accordance with a virtual desktopinfrastructure (VDI) template interacting with virtualization software.In at least one embodiment, the VDI template is created by an entity,such as a human expert, who has sufficient knowledge about the ESAcomputer system environment of the organization for which the ESA isbeing tested to provision an ESA testing computer system. By using theexpert created VDI, the computer system is provisioned with the correctoperating system, emulated hardware, correct supporting software, suchas libraries, Java™, database applications, application programinterfaces, drivers, hardware configuration, web server applications,and other software applications with which the ESA interacts, etc.

Utilizing the remotely provisioned ESA testing platform can, in at leastone embodiment, eliminate most of if not all setup issues thatconventionally occur, thus, eliminating, in at least one embodiment,60-80% of problems incurred during ESA testing. Furthermore, in at leastone embodiment, during testing, testers can record a “snapshot” of theprovisioned ESA testing platform when a problem occurs. In at least oneembodiment, a “snapshot” records data such as software, hardware, and/oruser interface state information. The snapshot can be transmitted to orconcurrently made available to ESA support personnel. In at least oneembodiment, the ESA support personnel can then promptly analyze andresolve the problem.

FIG. 2 represents an exemplary ESA testing environment 200. Testercomputers 202(0)-202(N) are used by testers to evaluate ESA resident onthe remote ESA testing platform 204, where “N” is an integer indexranging from 0 to the number of tester computers plus one. The ESAtesting platform 204 hosts an ESA environment that is set up by, forexample, an entity knowledgeable about an actual operating environmentfor which the ESA is being evaluated. The ESA testing platform 204includes M+1 computers 206(0)-206(M), where “M” is an integer indexranging from 0 to the number of ESA testing provisioned computers plusone. The tester computers 202(0)-202(N) communicate with the ESA testingprovisioned computers 206(0)-206(M) via a network 208. In at least oneembodiment, the network 208 includes the Internet. In at least oneembodiment, the ESA testing provisioned computers 206(0)-206(M) arecomputers in a cloud environment and are acquired via a web-based cloudcomputing service such as in the Amazon elastic computer cloud (AmazonEC2) web service. In at least one embodiment, the ESA testingprovisioned computers 206(0)-206(M) are are dedicated computers providedby the ESA owner or an entity contracted with or under control of theESA owner. In at least one embodiment, the ESA testing provisionedcomputers 206(0)-206(M) include virtualization software from, forexample, VMLogix, which is a part of Citrix Systems of Florida orVMware, Inc. of California.

FIG. 3 depicts an exemplary provisioning and ESA testing process 300.Referring to FIGS. 2 and 3, in operation 302, an entity knowledgeableabout an actual operating environment of an ESA creates a VDI template210. In at least one embodiment, the entity is a person who is an expertin the actual operating environment of an ESA. In at least oneembodiment, the VDI template 210 is created using any well-known VDItemplate creation software tool. The content of the VDI template 210serves as a management layer to provision the ESA testing platform 204.In at least one embodiment, the VDI template 210 includes information toprovision the ESA testing provisioned computers 206(0)-206(M) with thecorrect operating system, emulated hardware, correct supportingsoftware, such as libraries, Java™ database applications, applicationprogram interfaces, drivers, hardware configuration, web serverapplications, and other software applications with which the ESAinteracts, etc. In at least one embodiment, the VDI template 210 is aninstance of a master VDI template. In at least one embodiment, the VDItemplate 210 has a limited life window that provisions the ESA testingprovisioned computers 206(0)-206(M) for a predetermined amount of time,such as one (1) week. The predetermined amount of time is, for example,sufficient to complete testing of the ESA and limits costs associatedwith the acquiring the ESA testing provisioned computers 206(0)-206(M).

Operation 306 initiates ESA testing. In at least one embodiment, an ESAtester accesses a login web page, such as the login web page 300 of FIG.4. The tester enters the requested name, company, email id, accepts theterms and conditions, and selects the Submit button to obtain login datafor logging into the ESA testing platform 204. In at least oneembodiment, the login data includes a username, password, and link tolaunch the ESA hosted by the ESA testing platform 204. In at least oneembodiment, all clusters of supporting applications hosted by the ESAtesting provisioned computers 206(0)-206(M) are also launched so thatthe ESA testing platform 204 emulates an actual operating environment ofthe organization for which the ESA is being tested.

Testers can now test the ESA from the tester computers 202(0)-202(N) by,for example, interacting with the ESA. Exemplary interactions with theESA include sending data to exercise the functionality and otheroperational characteristics of the ESA. In at least one embodiment,during testing, testers record a “snapshot” of the ESA testing platform204 or of a specific computer or computers therein when a problemoccurs. The snapshot can be transmitted to or concurrently madeavailable to ESA support personnel. In at least one embodiment, the ESAsupport personnel can then promptly analyze and resolve the problem. Inat least one embodiment, upon completion of completion, results of thetests can be provided by the tester computers 202(0)-202(N) to one ormore user computers. In at least one embodiment, the users can monitorexecution of the ESA real-time via one or more remote connections to thetester computers 202(0)-202(N) and the results are evident frommonitoring execution or can also be provided to one or more usercomputers.

In at least one embodiment, in addition to eliminating, in at least oneembodiment, 60-80% of problems incurred during ESA testing, utilizingthe remotely provisioned ESA testing platform eliminates computeracquisition and setup time by the organization, and allows testers forthe organization to focus on testing the ESA. Accordingly, in at leastone embodiment, the time from the initiation of testing to completion isvirtually completely occupied by setup problem-free testing rather thanincurring and resolving setup issues. In at least one embodiment, ESAtesting can be accomplished within one (1) week, and total time frominitiation to deployment can be reduced from 6-12 months to 10 days.

Embodiments of the tester computers 202(0)-202(N) and ESA testingprovisioned computers 206(0)-206(M) can be implemented on a computersystem such as a general-purpose computer 500 illustrated in FIG. 5.Input user device(s) 510, such as a keyboard and/or mouse, are coupledto a bi-directional system bus 518. The input user device(s) 510 are forintroducing user input to the computer system and communicating thatuser input to processor 513. The computer 500 of FIG. 5 generally alsoincludes a video memory 514, main memory 515 and mass storage 509, allcoupled to bi-directional system bus 518 along with input user device(s)510 and processor 513. The mass storage 509 may include both fixed andremovable media, such as other available mass storage technology. Bus518 may contain, for example, 32 address lines for addressing videomemory 514 or main memory 515. The system bus 518 also includes, forexample, an n-bit data bus for transferring DATA between and among thecomponents, such as CPU 509, main memory 515, video memory 514 and massstorage 509, where “n” is, for example, 32 or 64. Alternatively,multiplex data/address lines may be used instead of separate data andaddress lines.

I/O device(s) 519 may provide connections to peripheral devices, such asa printer, and may also provide a direct connection to a remote servercomputer systems via a telephone link or to the Internet via an ISP. I/Odevice(s) 519 may also include a network interface device to provide adirect connection to a remote server computer systems via a directnetwork link to the Internet via a POP (point of presence). Suchconnection may be made using, for example, wireless techniques,including digital cellular telephone connection, Cellular Digital PacketData (CDPD) connection, digital satellite data connection or the like.Examples of I/O devices include modems, sound and video devices, andspecialized communication devices such as the aforementioned networkinterface.

Computer programs, such as the ESA, and data, such as VTI 208, aregenerally stored as instructions and data in a non-transitory massstorage 509 until loaded into main memory 515 for execution. Computerprograms may also be in the form of electronic signals modulated inaccordance with the computer program and data communication technologywhen transferred via a network.

The processor 513, in one embodiment, is a microprocessor manufacturedby Motorola Inc. of Illinois, Intel Corporation of California, orAdvanced Micro Devices of California. However, any other suitable singleor multiple microprocessors or microcomputers may be utilized. Mainmemory 515 is comprised of dynamic random access memory (DRAM). Videomemory 514 is a dual-ported video random access memory. One port of thevideo memory 514 is coupled to video amplifier 516. The video amplifier516 is used to drive the display 517. Video amplifier 516 is well knownin the art and may be implemented by any suitable means. This circuitryconverts pixel DATA stored in video memory 514 to a raster signalsuitable for use by display 517. Display 517 is a type of monitorsuitable for displaying graphic images.

In at least one embodiment, this novel use of, for example, VDItemplates, cloud computing, and virtualization software allows forefficient ESA testing. Additionally, sales cycles can be improved byremoving costly impediments to adopting ESA's. Furthermore, ESAdevelopment can provide more incremental changes due to reduceddeployment times and costs.

Although the present invention has been described in detail, it shouldbe understood that various changes, substitutions and alterations can bemade hereto without departing from the spirit and scope of the inventionas defined by the appended claims.

What is claimed is:
 1. A method comprising: receiving a request with acomputer from an end user using a computer to access an enterprisesoftware application (ESA) hosted by an EAS testing platform that isremote from the computer used by the end user; receiving data from thecomputer to test the ESA, wherein the remote EAS testing platform isprovisioned to emulate an actual operating environment for which the ESAis being tested; and testing the ESA in the computer.
 2. The method ofclaim 1 further comprising: providing test results from the testing ofthe ESA to the computer used by the end user.
 3. The method of claim 1further comprising: provisioning the remote EAS testing platform using avirtual desktop interface template.
 4. The method of claim 1 furthercomprising: accessing the EAS testing platform via cloud computing webservice.
 5. The method of claim 1 further comprising: recording a“snapshot” of the ESA testing platform during testing of the ESA.
 6. Themethod of claim 5 further comprising: transmitting the snapshot to acomputer system.
 7. An apparatus comprising: an enterprise softwareapplication (ESA) testing computer platform hosting an enterprisesoftware application, wherein the EAS testing platform includes one ormore computers that are remote from a computer used by an end userproviding data to test an ESA, wherein, during operation, the EAStesting platform is capable of receiving the data to test the ESA and toexecute the ESA.
 8. The apparatus of claim 7 wherein the EAS testingplatform is provisioned using a virtual desktop interface.
 9. Theapparatus of claim 7 wherein the EAS testing platform is accessible viaa cloud computing web service.
 10. The apparatus of claim 7 wherein theESA testing platform comprises one or more processors coupled to one ormore memories having the enterprise software application stored therein.11. The apparatus of claim 7 wherein the ESA testing platform isprovisioned to emulate an actual operating environment for which the ESAis being tested.
 12. The apparatus of claim 7 wherein the ESA testingplatform is further capable to: provide test results from the testing ofthe ESA to the computer used by the end user.
 13. The apparatus of claim7 wherein the ESA testing platform is further capable to: recording a“snapshot” of the ESA testing platform during testing of the ESA. 14.The apparatus of claim 7 wherein the ESA testing platform is furthercapable to: record a “snapshot” of the ESA testing platform duringtesting of the ESA.
 15. A computer readable medium comprising codestored therein and executable by a processor for: receiving a requestwith a computer from an end user using a computer to access anenterprise software application (ESA) hosted by an EAS testing platformthat is remote from the computer used by the end user; receiving datafrom the computer to test the ESA, wherein the remote EAS testingplatform is provisioned to emulate an actual operating environment forwhich the ESA is being tested; and testing the ESA in the computer. 16.The computer readable medium of claim 15 wherein the code is furtherexecutable by the processor for: providing test results from the testingof the ESA to the computer used by the end user.
 17. The computerreadable medium of claim 15 wherein the code is further executable bythe processor for: provisioning the remote EAS testing platform using avirtual desktop interface template.
 18. The computer readable medium ofclaim 15 wherein the code is further executable by the processor for:accessing the EAS testing platform via cloud computing web service. 19.The computer readable medium of claim 15 wherein the code is furtherexecutable by the processor for: recording a “snapshot” of the ESAtesting platform during testing of the ESA.
 20. The computer readablemedium of claim 19 wherein the code is further executable by theprocessor for: transmitting the snapshot to a computer system.
 21. Anapparatus comprising: means for receiving a request with a computer froman end user using a computer to access an enterprise softwareapplication (ESA) hosted by an EAS testing platform that is remote fromthe computer used by the end user; means for receiving data from thecomputer to test the ESA, wherein the remote EAS testing platform isprovisioned to emulate an actual operating environment for which the ESAis being tested; and means for testing the ESA in the computer.